projects / gnupg2.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 3a69788) | patch
gpg: Accept also armored data from the WKD.
authorWerner Koch <wk@gnupg.org>
Thu, 11 Apr 2019 07:54:28 +0000 (09:54 +0200)
committerDaniel Kahn Gillmor <dkg@fifthhorseman.net>
Thu, 22 Aug 2019 19:11:59 +0000 (20:11 +0100)
commit3f8490f79c7f51c67548b1e9ba097225fdc60768
tree6fdde5b2cbf482f12b5fab4467a4a020aaa08265tree | snapshot
parent3a69788f69107d93607fd1f8ca10c2f56bc4bb83commit | diff
gpg: Accept also armored data from the WKD.

* g10/keyserver.c (keyserver_import_wkd): Clear NO_ARMOR.
--

We may even adjust the specs to allow that.  It should not be a
problem for any OpenPGP implementation because armored keys are very
common and de-armoring code is de-facto a mandatory feature.

Signed-off-by: Werner Koch <wk@gnupg.org>
(cherry picked from commit dc4c7f65e32a0cddc075d06fa0132e099bcb6455)

Gbp-Pq: Topic from-2.2.16
Gbp-Pq: Name gpg-Accept-also-armored-data-from-the-WKD.patch
g10/keyserver.c diff | blob | history
Unnamed repository; edit this file 'description' to name the repository.